Skip to content

Conversation

@zulus
Copy link
Contributor

@zulus zulus commented Sep 11, 2025

Initial implementation:

  1. Upgrade @VUE packages to 3.0.7 + update TS LS to 5.0.0
  2. Implement tsserver/* notifications on Vue side
  3. Introduce JSTS interface (for LS lookup)
  4. Forward to JSTS - is not possible on ClientImpl side due no access to rootUri, if someone have idea howto move it to client side, please tell me

@zulus
Copy link
Contributor Author

zulus commented Sep 11, 2025

Now looks like problem with LSP4E, during processing for a moment in communication logs I see invalid file uris (relative to project root rather than absolute)

@zulus
Copy link
Contributor Author

zulus commented Sep 12, 2025

@zulus zulus force-pushed the vue3 branch 3 times, most recently from 1fd902b to 32e1fcf Compare September 13, 2025 16:21
@Override
public String toString() {
return "VUE Language Server: " + super.toString();
public void handleMessage(Message message, LanguageServer languageServer, URI rootURI) {
Copy link
Contributor Author

@zulus zulus Sep 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If someone have know howto move this to VueClientImpl I'll be happy to do this


@Override
public CompletableFuture<List<Object>> configuration(ConfigurationParams params) {
return CompletableFuture.supplyAsync(() -> {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Vue consume same configuration as HTML/CSS LS, so I just copy/paste

@Test
public void testJSXFile() throws Exception {
final IFile jsconfig = project.getFile("jsconfig.json");
jsconfig.create("{\"compilerOptions\":{\"jsx\":\"react\"}}".getBytes(), true, false, null);
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This fix broken test with new typescript server

@zulus zulus requested a review from vrubezhny September 13, 2025 16:50
@zulus
Copy link
Contributor Author

zulus commented Sep 15, 2025

/request-license-review

@github-actions
Copy link

/request-license-review

⚠️ Failed to request review of not vetted licenses.

Workflow run (with attached summary files):
https://github.com/eclipse-wildwebdeveloper/wildwebdeveloper/actions/runs/17739539134

@akurtakov
Copy link
Contributor

/request-license-review

@github-actions
Copy link

/request-license-review

⚠️ Failed to request review of not vetted licenses.

Workflow run (with attached summary files):
https://github.com/eclipse-wildwebdeveloper/wildwebdeveloper/actions/runs/17788348076

@akurtakov
Copy link
Contributor

[ ] INFO A review request was created https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/23371 .
[ ] INFO A review request was created https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/23372 .

@zulus
Copy link
Contributor Author

zulus commented Sep 18, 2025

License check problems: eclipse-dash/dash-licenses#448

Copy link
Contributor

@vrubezhny vrubezhny left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. Thanks Dawid!

The only thing is that usually we use spaces for tabs...
Not a big problem, but keeping this practice consistent helps avoiding the situations when you need to review a big file (all red and green) when the only one valuable line is actually added/removed/changed.

@vrubezhny vrubezhny merged commit a8d7cdb into eclipse-wildwebdeveloper:master Sep 19, 2025
13 of 20 checks passed
@zulus
Copy link
Contributor Author

zulus commented Sep 19, 2025

Arghhh I didn't notice that, sorry. Normally I just use Eclipse for Commiters settings and project scope .settings if available. Could you commit correct JDT formatter settings for this project?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants